chore(crypto): CRP-2682 Change key derivation used in VetKD to BLS12-381 hash_to_scalar #3736
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The old RO is no longer needed here, so removed
fspreiss
approved these changes
Feb 6, 2025
There was a problem hiding this comment.
Thanks, @randombit! Looks good to me. Maybe add a short PR descriptions. Also, ideally also @andreacerulli can look at this before merging.
altkdf
approved these changes
Feb 6, 2025
andreacerulli
approved these changes
Feb 13, 2025
marko-k0
pushed a commit
that referenced
this pull request
Feb 14, 2025
…381 hash_to_scalar (#3736) The approach originally used for the vetKD prototype for key derivation used SHAKE, largely as an artifact that we implemented an IBE demo as part of the same prototype, and SHAKE happened to be convenient for implementing IBE. However for production use of vetKD we will switch to using `hash_to_scalar`, a variant of RFC 9380's `hash_to_field`, since we already depend on the security of `hash_to_field` for implementing the hash to curve operation, upon which the security of vetKD depends. Thus we slightly reduce the number of cryptographic primitives vetKD depends on for its security.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The approach originally used for the vetKD prototype for key derivation used SHAKE, largely as an artifact that we implemented an IBE demo as part of the same prototype, and SHAKE happened to be convenient for implementing IBE. However for production use of vetKD we will switch to using
hash_to_scalar, a variant of RFC 9380'shash_to_field, since we already depend on the security ofhash_to_fieldfor implementing the hash to curve operation, upon which the security of vetKD depends. Thus we slightly reduce the number of cryptographic primitives vetKD depends on for its security.